Release 10.1A: OpenEdge Development:
Progress Dynamics Basic Development

Defining products and product modules

Progress Dynamics lets you segment your application into product modules so that you can organize your application objects based on the part of the overall application in which they are used. This section describes how to set up and use product modules. Product modules can represent any type of application organization you like. For example, they could correspond to different products and subproducts that you sell and deploy independently of one another, or they could be some other type of hierarchical organization that is meaningful to you. Setting up some sort of organizational structure helps you to:

Keep track of where your application components are located.
Determine what you need to deploy with your application.
Distribute and manage development work within your organization.
Locate objects quickly when assembling and maintaining parts of your application.

Progress Dynamics uses a strict two-level structure to organize components. The top level is called products and the second level product modules.

Every object you create in the Repository, whether it is entirely dynamic or whether it is a procedural object registered in the Repository, must have a product module assigned to it. Some kinds of objects might be very general-purpose and not really part of any specific application module (for example, window layouts that you create in the Layout Builder). For this reason, you might want to set up one or more modules that identify those general-purpose objects, such as a Design module.